Skip to content

Conversation

@ringabout
Copy link
Member

@ringabout ringabout commented Oct 10, 2025

ref #25056

https://github.com/nim-lang/nightlies/actions/runs/18053288396/job/51378922406#step:12:1572

bin/nim compile -f --incremental:off --compileonly --gen_mapping --cc:gcc --skipUserCfg --os:windows --cpu:loongarch64 -d:danger -d:gitHash:f4497c61584dca8acd489ceb7ba862b150f5cf55 compiler/nim.nim

loongarch64 is applied to all the platforms wrongly. Presumably it was caused by the order?

@ringabout ringabout changed the title nightlies: fixes order? nightlies regressions: fixes order? Oct 10, 2025
@ringabout ringabout changed the title nightlies regressions: fixes order? nightlies regressions: CPU order matters for C courses? Oct 10, 2025
@ringabout ringabout changed the title nightlies regressions: CPU order matters for C courses? nightlies regressions: CPU order matters for C sources? Oct 10, 2025
@Araq Araq added the merge_when_passes_CI mergeable once green label Oct 10, 2025
@Araq Araq merged commit 3962264 into devel Oct 10, 2025
21 checks passed
@Araq Araq deleted the pr_fest branch October 10, 2025 17:11
@github-actions
Copy link
Contributor

Thanks for your hard work on this PR!
The lines below are statistics of the Nim compiler built from 3962264

Hint: mm: orc; opt: speed; options: -d:release
183144 lines; 7.415s; 661.699MiB peakmem

@ringabout
Copy link
Member Author

The issues is actually that there is a hard limit for max cpus: #25219, which set to 20 while there is a 21 cpus now!

ringabout added a commit that referenced this pull request Oct 11, 2025
narimiran pushed a commit that referenced this pull request Oct 13, 2025
ref #25056

https://github.com/nim-lang/nightlies/actions/runs/18053288396/job/51378922406#step:12:1572

```
bin/nim compile -f --incremental:off --compileonly --gen_mapping --cc:gcc --skipUserCfg --os:windows --cpu:loongarch64 -d:danger -d:gitHash:f4497c61584dca8acd489ceb7ba862b150f5cf55 compiler/nim.nim
```

`loongarch64` is applied to all the platforms wrongly. Presumably it was
caused by the order?

(cherry picked from commit 3962264)
Araq pushed a commit that referenced this pull request Oct 13, 2025
ref #25217

The issues is actually that there is a hard limit for max cpus in
niminst: #25219, which set to 20
while there is a 21 cpus now
narimiran pushed a commit that referenced this pull request Oct 14, 2025
ref #25217

The issues is actually that there is a hard limit for max cpus in
niminst: #25219, which set to 20
while there is a 21 cpus now

(cherry picked from commit c0fa868)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge_when_passes_CI mergeable once green

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants